I think you may have meant to highlight 9 and 13? The function names?

I think 14 is correct, it's the line with return $this->cache->increment('counter');

You are right. Both lines need to be udpated.

I think these should be lines 10 and 15 to highlight the CacheManager line and the return this-> ... line

I think 14 is correct, it's the line with return $this->cache->increment('counter');

I didn't pick up on this when reviewing the original PRs, so forgive me for asking this late: where does the database name come from? Are you relying on whatever is configured through the corresponding connection option (for both this and lock_collection)?

The database name is set in the database connection configuration. Do you think we should add an option to change the database name for cache and lock?

You can also consider allowing a namespace for the collection and lock_collection options, and parsing out a database name by exploding on a dot character (no issue since it's prohibited in each part per Naming Restrictions.

Otherwise, I'm fine keeping this as-is and revisiting if/when someone asks for further customization.

Tracking this feature: PHPORM-176

Should collection and various lock options be specified here?

Also, is there any significance to the line break between default and stores in the configuration array? I believe you're already emphasizing the default line, so I don't think a line break is necessary for readability.

Here, I rely on the default values. Do you think I should make a note of that?

Calling out your reliance on default values makes sense to me.

I was mostly concerned with collection. The MongoLock constructor requires a value for its Collection parameter, and I didn't see where the default gets supplied.

"connection" is required, "collection" has a default value which is cache. These 2 words are so similar that they can easily be confused.

The default is applied in the service provider.